docs(rokt): session management guidance for the kit - #821
Conversation
PR SummaryLow Risk Overview Adds a kiosk/shared-device pattern: call Reviewed by Cursor Bugbot for commit f3e3292. Bugbot is set up for automated code reviews on this repo. Configure here. |
📦 SDK Size Impact ReportMeasures how much the SDK adds to an app's size (with-SDK minus without-SDK).
➡️ SDK size impact change is minimal. Raw measurementsTarget branch (main): {"baseline_app_size_kb":84,"baseline_executable_size_bytes":75464,"with_sdk_app_size_kb":1920,"with_sdk_executable_size_bytes":76312,"sdk_impact_kb":1836,"sdk_executable_impact_bytes":848,"xcframework_size_kb":6648}This PR: {"baseline_app_size_kb":84,"baseline_executable_size_bytes":75464,"with_sdk_app_size_kb":1920,"with_sdk_executable_size_bytes":76312,"sdk_impact_kb":1836,"sdk_executable_impact_bytes":848,"xcframework_size_kb":6648} |
a2a87e1 to
d97c61c
Compare
c68e68c to
99676f6
Compare
Pull Request is not mergeable
Pull Request is not mergeable
99676f6 to
e596e60
Compare
Documents the automatic identity-driven session behaviour (typed transitions), the recommended kiosk pattern (logout between customers), the manual MPRokt.clearSession escape hatch, and when the new session begins. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
trunk-check failed with "1 unformatted file" -- this PR's only file. Reading it to fix the formatting surfaced a larger problem: the page documented the automatic identity-driven reset, which was removed from the kit before shipping. Every substantive claim had gone stale -- "the kit ends the Rokt session whenever the mParticle user changes", the identity-transition table, and "No integration code is needed". The kiosk guidance was the damaging part. It told partners to log the user out between transactions and let the kit reset for them; with no automatic path that produces no reset at all, which is exactly the shared-terminal session bleed this work exists to fix. Publishing it would have handed the affected partners the wrong instruction. Rewritten to describe what ships: no automatic reset, explicit clearSession at the transaction boundary, and why the identity signal was rejected -- an MPID can move mid-journey for one customer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
e596e60 to
f3e3292
Compare
What
Kit README section documenting session management — the mParticle-side counterpart of the SDK docs in ROKT/rokt-sdk-ios#299:
MPRokt.clearSession()escape hatch from feat(rokt): add MPRokt clearSession passthrough #818, when the new session begins, no-op/idempotency notes, and the collision-safety of combining manual + automaticDocs only. Stacked on #819 — its base is that branch; retargets to the default branch cleanly once #819 lands.
🤖 Generated with Claude Code